Skip to content

chore(release): @wippy-fe 0.0.41 + Web Host CDN 1.0.41 + facade 0.6.17 (EE2-2274)#19

Merged
AndrewKirkovski merged 3 commits into
demo/chat-web-component-tabfrom
chore/release-1.0.40
Jun 29, 2026
Merged

chore(release): @wippy-fe 0.0.41 + Web Host CDN 1.0.41 + facade 0.6.17 (EE2-2274)#19
AndrewKirkovski merged 3 commits into
demo/chat-web-component-tabfrom
chore/release-1.0.40

Conversation

@AndrewKirkovski

Copy link
Copy Markdown
Contributor

EE2-2274 — consume the 1.0.41 stack + theme-persistence examples

Upgrades the consumer to the 1.0.41 release and adds the theme-persistence login examples. Base is demo/chat-web-component-tab (same integration branch as the 1.0.40 release PR #17).

Stack bump

  • @wippy-fe/*^0.0.41 across all 9 frontend packages (apps + web components); lockfiles regenerated against the published registry.
  • Web Host CDN ref → webcomponents-1.0.41 in both app.html dev-proxy entries.
  • wippy.lock: wippy/facade 0.6.16 → 0.6.17 (theme persistence + Jet SSR shell), plus the modules refreshed by wippy update (keeper, session, views, agent, dataflow, llm, relay, uploads, users).

Theme-persistence examples

  • Jet login (src/app/api/login.jet + login_jet.lua): server-side reads the theme cookie and bakes the w-theme-* class onto <html> for zero-flash; served at /login. Wiring in src/app/api/_index.yaml, src/app/_index.yaml, src/app/deps/_index.yaml (theme_persist: cookie, theme_storage_key).
  • Static login (static/login.html, at /app/login.html): the same flow via the facade's served theme-persist.js.
  • Both login switchers reuse the in-app sidebar switcher designtabler:device-desktop / sun / moon icons and the segmented track + raised active pill with a primary-tinted icon (light + dark).
  • e2e/theme-persistence.spec.ts: Playwright coverage (endpoint/config, cookie SSR, switcher persistence).

Verification

  • Smoke gates 2A–2G green (built host, consumer-vs-local-npm, replace-mode, fully-published non-dev boot).
  • Fully-published boot: facade 0.6.17 from the hub, @wippy-fe@0.0.41, CDN host 1.0.41 — every route + web component rendered with live data; theme switch → cookie → reload persists with no flash; only webcomponents-1.0.41 on the wire, zero failed requests.

Counterpart PRs: facade wippyai/framework#66 (publishes wippy/facade@0.6.17); Web Host gen-2-chat 1.0.41 (@wippy-fe@0.0.41 published).

- Static login (static/login.html) and Jet login (src/app/api/login.jet +
  login_jet.lua, served at /login via a public `web` router) examples, each with a
  segmented icon theme switcher that persists via window.wippyThemePersist. The Jet
  login renders the theme server-side from the cookie (no flash). login_path -> /login.
- Opt in to facade theme_persist=cookie (key @wippy-theme-mode) in src/app/deps;
  wippy.lock `replacements:` points wippy/facade at the local checkout for testing.
- Playwright e2e (e2e/theme-persistence.spec.ts): theme-persist.js endpoint + config,
  cookie SSR for shell + Jet login, and switcher persistence (6 cases).
- Bump @wippy-fe/* frontend deps -> ^0.0.41 and CDN refs (login stylesheets +
  app.html dev-proxy) -> 1.0.41. Lockfiles regenerate on the next clean rebuild.
…ade 0.6.17 + module update

- Regenerate 9 frontend package-lock.json against published @wippy-fe@0.0.41
  (clean reinstall; package.json already at ^0.0.41).
- wippy.lock: wippy/facade 0.6.16 -> 0.6.17 (theme persistence + Jet SSR shell)
  plus the modules refreshed by `wippy update` (keeper, session, views, agent,
  dataflow, llm, relay, uploads, users).
Both login examples (static static/login.html and Jet src/app/api/login.jet)
now mirror the sidebar switcher in app.vue: tabler device-desktop / sun / moon
icons and the segmented track + raised active pill with a primary-tinted icon
(was a separate icon set with a solid primary-filled active segment). Adds
.w-theme-dark overrides for the dark track/pill. CSS + SVG only; no behavior change.
@AndrewKirkovski AndrewKirkovski merged commit fce6b97 into demo/chat-web-component-tab Jun 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant